Skip to content

Instantly share code, notes, and snippets.

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

@eliottness
eliottness / README.md
Last active September 8, 2026 10:04
Bitwarden SSH agent in WSL2 via a systemd user service (socat + npiperelay) — with the gotchas that make ssh-add hang

Bitwarden SSH agent in WSL2 (via systemd)

Use the SSH keys stored in your Windows Bitwarden Desktop vault from inside WSL2ssh, git, ssh-add, etc. — managed by a systemd user service instead of a fragile .zshrc snippet.

This bridges the Windows OpenSSH-agent named pipe that Bitwarden exposes (\\.\pipe\openssh-ssh-agent) to a Unix socket inside WSL using npiperelay + socat.

@Hotrod369
Hotrod369 / 1_Sieve_Script_Cheatsheet.md
Last active September 8, 2026 09:57
This Gist provides a comprehensive cheatsheet for Sieve scripts, covering various objects, attributes, parameters, and their possible values. Sieve is a powerful scripting language for filtering and organizing emails, commonly used with email clients and servers. This cheatsheet includes tests, actions, comparators, and extensions to help you cr…

"3 step" + a link to a paper/article/report is standing shorthand for: read the full source (not just abstract or preview), then write one continuous summary in three layers of increasing length. Layer 1 is one paragraph: the whole piece at maximum compression, a complete stopping point on its own. Layer 2 is two paragraphs that continue from Layer 1 without restating it, adding the next tier of detail (mechanism, key evidence, how the result was produced). Layer 3 is three paragraphs that continue from Layer 2 (methodology specifics, numbers, context, limitations, implications). Every prefix (1, 1+2, 1+2+3) must read as a self-contained summary at its depth. Mark the three layers visibly so the reader can stop at a boundary: a short bold label on its own line before each layer ("Layer 1", "Layer 2", "Layer 3"). No other headers or formatting inside the layers. Nothing is repeated across layers; each only adds. Compression is the point; analysis serves it. Write in plain, direct sentences for a smart reader o

/*
* Copyright 2026 Kyriakos Georgiopoulos
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
@kn9ts
kn9ts / GPLv3.md
Last active September 8, 2026 09:44
GPLv3 explained

GPL3 LICENSE SYNOPSIS

TL;DR* Here's what the license entails:

1. Anyone can copy, modify and distribute this software.
2. You have to include the license and copyright notice with each and every distribution.
3. You can use this software privately.
4. You can use this software for commercial purposes.
5. If you dare build your business solely from this code, you risk open-sourcing the whole code base.
@ongkiii
ongkiii / IPA-Sources.md
Last active September 8, 2026 09:44
REPOS/TELEGRAM CHANNELS LIST BY u/angkitbharadwaj
@cirippo
cirippo / ReadMe.md
Last active September 8, 2026 09:41
Download Google Drive protected PDF without TrustedScriptURL error at higher resolution

Easy step by step guide to download view only PDF from Google Drive - no TrustedScriptURL error and better quality


  1. Open the document in Google Docs
  2. Zoom in 2 times using Ctrl and + (VERY IMPORTANT!)
  3. Open Developer Tools
  4. Hit Ctrl + R to reload the document.
  5. Scroll to the bottom of the document to load all pages.
  6. To check if all pages are loaded, go to "Network" tab, type "img" in search bar. At the bottom bar you see "xx/yyy requests", "xx" must be equal to document's pages; if not scroll up to load missing pages
  7. Go to "Console" tab
  8. Paste the updated and improved script (download_pdf.js) that avoids TrustedScriptURL error and allows better file's quality